|
|
Hi Jewoo, We have listed some issues that Mr. Yoon has forward to TVS, please monitor it. |
|
|
Hi Jason and Bryan, We have confirmed that this behavior is same as the reference model(BKO-AT800). BTW let us discuss with SKB for their design about this, and then reply to you. In addition, could you help to double check that this issue will block CTS pass? Thanks. |
|
|
Hi Jewoo, This item is included in Smoke test, We must pass smoke test in each official release. |
|
|
Hi Jason, Once we will discuss about this issue with other partners and SKB. Could you help to check if there is a way to avoid the fail for this issue like other smoking test issues? BTW if there is any specific document for Android TV requirements except CDD, could you share it with us for our understanding? Thanks. |
|
|
Hi Jewoo, 1. We don't have any way to avoid this fail, because we used standard suspend/resume flow before. Currently, TVS modified the suspend/resume flow for SKB's requirement. I think TVS should work with Amlogic to fix this issue. 2. According to Google contract, we can not share the google documents to you. |
|
|
Hi Jason, Could you let me know the test item or case number of Smoke Test for this issue? If possible, please provide the test case details as well. We need to discuss about SKB standby scenario with it. Thanks. |
|
|
Hi Jweoo, Please check the 2nd row of attachment. smoketest.jpg (79,638 bytes) |
|
|
Hi Jewoo, According to SW Release Plan, could you check the scenario before this Wednesday (5/8), we are going to release new fw on this Wednesday. |
|
|
Hi Jason, I have discussed with SKB about standby scenario, and they don't want to change it at this time(Eagle project). So please check if the attachment is enough or not to get waiver from 3PL for this issue. The attachment has been extracted from RFP document, because there is no specific document including standby/wake-up scenario in SKB, and we can't share overall RFP document due to security issue. Thanks. |
|
|
|
|
|
Hi Jewoo, I think this document will not help us to waive this issue, because we didn't see the "reason" why our firmware can not support wake on casting. |
|
|
It implemented in v39. |
|
|
Hi Mr. Yoon, I reopen this issue for BTF. Because SPtek had modified Android standby flow, so we can't use mobile device casting feature to wake STB from active standby. In last year, I informed this issue to TVS, but they don't know how to fix it, During my business trip in Korea, TVS told us the "wake broadcast" command, so I can help TVS fix this issue. In BTF project, I tried to use same broadcast command to wake the STB from standby, but it's not work, I think the "wake broadcast" was designed by TVS in Android P, it can not applied into BTF project. Please discuss it with SPtek. |
|
|
hi Jason. I heard We send INTENT to TVS service to finish implementation for cast wakeup. you know which INTETNT was used in android P. SPtek want to help this item. Thanks. |
|
|
Hi Mr. Jason Park, We used the following intent to wake the device. com.skbtv.tv.wakeup I think this intent was designed by TVS. I use this intent in BTF project. but it is not work. |
|
|
hi Jason.liang. Didn't you still work it? sptek reported it is done on jira-site. which version is used for your test ? |
|
|
Hi Mr. Jason Park Our QA has verified this issue. We can use mobile phone to wake STB from standby by casting function. But they found another issue. The problem is that they cannot enter standby mode stably. Sometimes it will succeed and sometimes it will fail. When STB enters the standby mode successfully, Sometimes it fails to wake up by RCU powerkey. I will close this issue and post this problem to [BTF] Google Certification. |
- yk.jung ( (ALTech) Younkwang Jung ) developer
